docs: add Brazilian Portuguese and Russian READMEs - #770
Closed
2160039878-cyber wants to merge 1 commit into
Closed
Conversation
cevheri
marked this pull request as draft
September 10, 2026 06:40
Member
|
are you native Portuguese speaker |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Brazilian Portuguese and Russian readers currently have no localized entry point. Add two abridged READMEs covering the project, supported engines, installation, quick start, security, AI data flow, and contribution requirements. Both translations share the language-switcher and drift-guard update in this PR.
Type of Change
Related Issue
Closes #594
Closes #610
Claims: Portuguese, Russian.
Changes Made
README_pt.md(251 lines) andREADME_ru.md(254 lines), following the existing abridged scope. Preserve the 16 canonical engine names and quote install-table commands verbatim.main, and register both new files inLOCALIZED.Testing
Local validation on
a767100f700c10cf44a4de0aaca02b4c00b8f31c:bun run test:unit --isolate --pass-with-no-tests -t 'parseTables|table lookup|extraction|checkReadmes|readme-check CLI': 45 passed, including all 31 drift-guard tests. The name filter also selected 14 existing tests.bun run readme:check: both new translations match the canonical engine set and install commands.bun run format,lint,typecheck,knip,chart:check,channels:showcase:check,security:check, andbuild: passed.The complete local
bun run test/ coverage run was not repeated: this Windows environment lacks the Helm/chart test prerequisites and has known unrelated SQLite file-lock limitations. Full-suite, coverage, E2E and engine checks are left to the required CI workflows. No installation command in the documentation was executed as part of translation validation.Test Environment
2f4ae61216956824410ba2f16bae3f697348afe3Checklist
bun run test:coverageandbun run coverage:check)Additional Notes
Prepared with Codex, including AI-assisted translation and test authoring. Technical claims, terminology, commands, and links were reviewed and revised against the source documents; no independent native-speaker review is claimed. Language-quality feedback is welcome. The drift guard verifies technical invariants, not linguistic quality.